Unified and best messaging systems for communication devices

ABSTRACT

A unified messaging system which can provide messaging services for a plurality of different “message types” is disclosed. The unified messaging system can serve as a single interface to a number of messaging services provided by various messaging components which use different message types (e.g., mail server). A unified message type is implemented and presented to a user as an abstract message. In addition, the unified messaging system can automatically determine, based on a first selected feature, if one or more message types should be used. A particular message type can also be automatically selected as a “best message type” based on one or more selected options.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/722,343, filed Mar. 11, 2010, entitled “Unified and Best MessagingSystems for Communication Devices,” which is a continuation of U.S.patent application Ser. No. 10/981,970, filed Nov. 4, 2004, entitled“Unified and Best Messaging Systems for Communication Devices,” now U.S.Pat. No. 7,756,256, which claims the benefit of Provisional U.S. PatentApplication No. 60/525,564, filed Nov. 26, 2003, entitled “BestMessaging,” each of which is incorporated herein by reference in itsentirety.

BACKGROUND OF THE INVENTION

The present invention relates to communication systems, and moreparticularly, to a messaging system used for exchanging informationbetween various communication environments.

Modern communication systems facilitate communication of information inmany forms and between various communication devices (e.g., computers,wireless terminals or devices, cellular telephones, pagers, personaldigital assistants, etc.). Given the popularity of modern communicationsystems, extensive efforts have been made by a number of entities toprovide users with increasingly better communication devices. Thesedevices, among other things, provide a messaging system that allowsusers to exchange information. The messaging system can serve as aninterface to a messaging services provided by a particular messagingprovider or messaging server.

Typically, handheld communication devices have a relatively small amountof display space available in comparison to desktop devices (e.g., apersonal desktop computer). Hence, the same solutions used to solveproblems encountered in the desktop environment, may not be as effectivefor the handheld communication devices.

Moreover, the large number of different “message types” used today hasintroduced new challenges. A “message type” may, for example, pertain toa particular messaging protocol (e.g., SMS/EMS, WAP 275/276, imode mail,SMTP, POP3) and/or message formats (e.g., text, slideshow). This meansthat many message types can be formed, for example, when a particularmessage format is used with a particular messaging protocol. By way ofexample, considering only two message protocols SMS and MMS, manymessage types can be appropriately used (e.g., SMS-Text, SMS-Rich (EMS),MMS-slideshow (SMIL), MMS-multipart (inline)). Each message type has itsown technical capabilities, limitations, and other particular attributes(e.g., message size limit, cost). Moreover, some message protocols maynot support a particular format. These complexities have negativelyaffected the experience of the users of modern messaging systems.Typically, these users have to learn about various messaging interfaces(e.g., SMSC, MMSC, I-mode server, SMTP server, POP server). As a result,some users of messaging systems had to learn the technical capabilitiesand limitations of various message protocols, formats, and othertechnical details in order to exchange messages. Other users have oftenbeen frustrated and/or confused when a feature (or option) that isinappropriate and/or not desired has been selected.

Accordingly, there is a need for alternative messaging system.

SUMMARY OF THE INVENTION

Broadly speaking, the invention relates to a messaging system in acomputing environment that may include a plurality of different “messagetypes”. A “message type” may, for example, pertain to a particularmessaging protocol and/or message format. In general, a message type hasone or more distinguishable characteristics which may be entirely basedon form or conventions used to process the message.

In accordance with one aspect of the invention, a unified messagingsystem can provide messaging services in a computing environment thatmay include a plurality of different “message types”. As will beappreciated, the unified messaging system can serve as a singleinterface to a number of messaging services provided by variousmessaging components which use different message types (e.g., mailserver).

In one embodiment, the unified message system generates a unifiedmessage type which can be implemented and presented to a user as anabstract message that does not pertain to a particular message type. Inaddition, the unified messaging system can provide the user with a setof abstract features (or options) that the user can select withouthaving to know or identify a particular message type. The abstractfeatures can, for example, include a set of abstract operations that canbe performed on a abstract message (e.g., send, receive, attach,slideshow, acknowledge receipt, phone), as well as other componentswhich may be useful in a messaging environment, and possibly combinedwith one or more abstract operations (e.g., “send bob, “send bobacknowledgment receipt,” send bob slideshow”). Moreover, the unifiedmessaging system can automatically determine, based on a first selectedfeature, if one or more message types should be used. Message types thatshould not be used are automatically eliminated and the user can bepresented only with a set of options that are still viable based on whathas already been selected. In addition, a particular message type isautomatically selected as a “best message type” based on one or moreabstract selected options. The unified message can then be transformedto a particular message type (i.e., best message type) and transmitted.It should be noted that a particular message type may also betransformed to an abstract message which is presented to the user. Inany case, a user can use a single messaging interface to servicesprovided by various messaging servers. In addition, the user may use theservices without having to know or select a particular message type asan appropriate message type can be automatically selected for the user.It should also be noted that only viable features (or options) can bedisplayed for the user in accordance with one embodiment of theinvention. As a result, the user of the messaging system is notconfronted with many potentially inappropriate features (or options).Hence, the user's experience is significantly improved and user will befree form learning the technical limitations and capabilities associatedwith various message types.

The invention can be implemented in numerous ways, including as amethod, an apparatus, and computer readable media. Several embodimentsof the invention are discussed below.

Other aspects and advantages of the invention will become apparent fromthe following detailed description, taken in conjunction with theaccompanying drawings, illustrating by way of example the principles ofthe invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will be readily understood by the followingdetailed description in conjunction with the accompanying drawings,wherein like reference numerals designate like structural elements, andin which:

FIG. 1 illustrates a communication system including an enhancedcommunication device in accordance with one embodiment of the invention.

FIG. 2A depicts a unified messaging system in a computing environment inaccordance with one embodiment of the invention.

FIGS. 2B-2D depict an abstract message in connection with a messageencoder/decoder.

FIG. 3 depicts a unified messaging method in accordance with oneembodiment of the invention.

FIG. 4 depicts a message transmission method for generating andtransmitting a message in accordance with one embodiment of theinvention.

DETAILED DESCRIPTION OF THE INVENTION

The invention pertains to a messaging system in a computing environmentthat may include a plurality of different “message types”. A “messagetype” may, for example, pertain to a particular messaging protocoland/or message format. In general, a message type has one or moredistinguishable characteristics which may be entirely based on form orconventions used to process the message.

In accordance with one aspect of the invention, a unified messagingsystem can provide messaging services in a computing environment thatmay include a plurality of different “message types”. As will beappreciated, the unified messaging system can serve as a singleinterface to a number of messaging services provided by variousmessaging components which use different message types (e.g., mailserver).

In one embodiment, the unified message system generates a unifiedmessage type which can be implemented and presented to a user as anabstract message that does not pertain to a particular message type. Inaddition, the unified messaging system can provide the user with a setof abstract features (or options) that the user can select withouthaving to know or identify a particular message type. The abstractfeatures can, for example, include a set of abstract operations that canbe performed on a abstract message (e.g., send, receive, attach,slideshow, acknowledge receipt, phone), as well as other componentswhich may be useful in a messaging environment and possibly combinedwith one or more abstract operations (e.g., “send bob,” “send bobacknowledge receipt,” “send bob slideshow”). Moreover, the unifiedmessaging system can automatically determine, based on a first selectedfeature, if one or more message types should be used. Message types thatshould not be used are automatically eliminated and the user can bepresented only with a set of options that are still viable based on whathas already been selected. In addition, a particular message type isautomatically selected as a “best message type” based on one or moreabstract selected options. The unified message can then be transformedto a particular message type (i.e., best message type) and transmitted.It should be noted that a particular message type may also betransformed to an abstract message which is presented to the user. Inany case, a user can use a single messaging interface to servicesprovided by various messaging servers. In addition, the user may use theservices without having to know or select a particular message type asan appropriate message type can be automatically selected for the user.It should also be noted that only viable features (or options) can bedisplayed for the user in accordance with one embodiment of theinvention. As a result, the user of the messaging system is notconfronted with many potentially inappropriate features (or options).Hence, the user's experience is significantly improved and user will befree form learning the technical limitations and capabilities associatedwith various message types.

Embodiments of the invention are discussed below with reference to FIGS.1A-4. However, those skilled in the art will readily appreciate that thedetailed description given herein with respect to these figures is forexplanatory purposes as the invention extends beyond these limitedembodiments.

FIG. 1 illustrates a communication system 100 including an enhancedcommunication device 102 in accordance with one embodiment of theinvention. The enhanced communication device 102 can, for example, beimplemented as a computer, a remote wireless device, a cell phone, apersonal digital assistant, etc. The enhanced communication device 102can communicate with a communication network 103. The communicationnetwork 103 may be or include, for example, the Internet, one or morecampus intranets, local area networks (LANs), wide area networks (WANs),or wireless telecommunication networks, e.g., a cellular digital packetdata (CDPD) network, a global system for mobile (GSM) communicationsnetwork, a time division multiple access (TDMA) network, a personaldigital cellular (PDC) network, or a personal handy-phone system (PHS)network. In any case, the communication network 103 facilitatescommunication between the enhanced communication device 102 and variousother components of the communication system 100. These components can,for example, include a server 104, a conventional communication device106 or another enhanced communication device 108.

For ease of illustration, the enhanced communication device 102 isdepicted in FIG. 1 as providing a unified messaging system 112. However,as will be appreciated by those skilled in the art, the operationsrelated to unified messaging system 112 can entirely or partially beperformed at the server 104. Alternatively, the unified messaging system112 can be implemented as a part of the hardware and/or software in theenhanced communication device 102. In any case, the unified messagingsystem 112 provides a unified messaging environment where variousprotocols and message types may be integrated. Moreover, in theintegrated environment provided by the unified messaging system 112, theuser does not have to learn about the capabilities and limitations ofvarious protocols and/or message types that can be used to exchangemessages partly because a unified messaging system is provided. Inaddition, the unified messaging system 112 provides many other featureswhich further enhance the user's experience. These features include aunified inbox for storing various types of messages, and a “bestmessaging” feature that, among other things, displays a selected set ofviable options for the user based on the options that the user hasalready selected. Furthermore, the “best messaging” feature canautomatically select the appropriate mechanism (e.g., protocol, messagetype) to perform a desired option (delivering a message, viewing amessage, etc.). “Best messaging” is further described below.

To further illustrate, FIG. 2A depicts a unified messaging system 112 inaccordance with one embodiment of the invention. As shown in FIG. 2A,several architectural levels that may be used to implement the unifiedmessaging system 112. These architectural levels include: unifiedmessenger 202, application programming interface (API) 204, devicesoftware 206 and device hardware 208. The unified messenger 202 uses theAPI 204 as an interface to device software 206 which in turn interactswith a device hardware 208. Thus, the unified messenger 202 can performvarious messaging tasks (e.g., send, receive messages) via the devicehardware 208. Moreover, the unified messenger 202 can perform messagingtasks using a variety of protocols (e.g., SMS/EMS, WAP275/276, imodemail, SMTP, POP). In other words, a single messaging application,namely, the unified messenger 202 may be used to interact with variousprotocols and message types. Hence, a user may be presented with asingle unified messenger 202 to perform various messaging tasks usingdifferent messaging protocols and/or messaging types. In addition, aunified inbox 210 can be provided for the user. The unified inbox 210can be used to store various message types despite the protocols used totransmit them. It should be noted that the unified messaging system 112can behave as a client and use various protocols to interact withvarious messaging servers.

As shown in FIG. 2A, the messaging system 112 also provides an abstractmessage 212 and a message encoder/decoder 214. The abstract message 212can be a conceptual representation of a generic message that mayultimately be mapped to a particular protocol and/or message form (“amessage type”). The message encoder/decoder 214 can facilitate themapping of the abstract message to a particular message type, and viceversa.

Referring now to FIG. 2B, the abstract message 212 is depicted inconnection with the message encoder/decoder 214. In addition, a set offeatures 216 are depicted. The set of features 216 represents a set ofoptions that may be initially displayed for a user (e.g., send, compose,read, etc.). It should be noted that these set of features 216 canrepresent a set of abstract options that are available. In other words,the set of features 216 do not necessarily pertain to a particularmessage type. Also, selection of an initial particular feature (e.g. F1)results in storing one or more states (e.g., state 1) in the abstractmessage 212. When a state is added to the abstract message 212, themessage encoder/decoder 214 determines based on the states currently inthe abstract message whether a particular message type can be used. Inaddition, an updated feature set 218 may be presented based on thisdetermination. In other words, one or more options may be eliminatedbased on the states stored in the abstract message 212. As a result, theuser can be provided only with a set of viable options. Moreover, theuser does not need to select a particular message type. An appropriatemessage type can be selected and automatically generated by the messageencoder/decoder 214. Hence, the user can interact with a set of abstractfeatures without knowing about the specific message types. Options thatmay not be viable or preferred after a selection of another option canbe automatically eliminated and a message type (message protocol and/orformat) can automatically be selected for the user.

It should be noted that the states I-N may be organized, for example, invarious categories: composition layout (e.g., attachment, imageinlining, slides), formatting (e.g., text, character set), preferences(e.g., priority, recipient acknowledgment), rules (e.g., use MMS if morethan two (2) SMS messages have been sent), addressing message (e.g., toalias “Bob”): In general, any messaging attribute may be presented withone or more states which may be used to provide the user with a set ofviable options. In addition, one or more states of the abstract messagecan be used to select a particular message type that is ultimatelygenerated for the user.

As shown in FIG. 2C, when a feature F1 (“add slideshow”) is selected, acomposition state “add slideshow” can be added to the abstract message212. This can, for example, result in selection of the “mms/slideshow”message type. It should also be noted that abstract features may also bepresented to the user. Referring to FIG. 2D, an abstract “send” feature250 can be presented to the user. The user then may select anotherabstract feature (or option), for example “Bob” 252 which can be anemail alias. In this example, “Bob” is known only as an email address.As a result, the abstract message 212 will include a state “email”.Hence, email is automatically selected (254) to send the message.

As another example, adding a slide would add a new slide layout to thecontents of the message. The MMS protocol would understand this newlayout and allow it, so MMS remains as a viable option along with allthe features of MMS. However, the SMS protocol would not understand thisnew layout and would reject it, so SMS would not remain a viable option.As another example, on a different message, adding a email address isallowed because SMTP & MMS both enable that feature. Once the emailaddress is added the MMS & SMTP protocol would understand the addresstype and allow it, so MMS remains as a viable option along with all thefeatures of MMS. The SMS protocol would not understand the address typeand would reject it, so SMS would not remain a viable option.

FIG. 3 depicts a unified messaging method 300 in accordance with oneembodiment of the invention. Initially, an abstract unified message anda set of abstract messaging features are provided (302). It should benoted that the abstract unified message can represent a plurality ofdifferent message types. Next, an initial set of abstract features aredisplayed (304). These abstract features can be selected by the user. Aswill be appreciated, the abstract features do not need to pertain to aparticular message type. Rather, the abstract feature can represent, forexample, an abstract operation (e.g., send message) that can beperformed using various message types. As another example, an abstractfeature may represent another option (e.g., “Bob”) representing anotheruser.

In any case, when it is determined (306) that an abstract feature hasbeen selected 306, it is determined, based on at least one selectedabstract feature, which message type should be used (308(a)) and/or itis determined whether a set of other abstract features should bedisplayed (308(b)) for the user. Based on at least one selected feature,it is determined whether one or more features should be displayed.Accordingly, an updated set of features can be displayed (312) for theuser. Thereafter, it can be determined whether another abstract featurehas been selected 306. When it is determined 310 that no more featuresshould be displayed (i.e., the message should be sent), the abstractmessage is transformed (314) to a particular message type so that it canbe transmitted (316) using an appropriate message protocol and messageformat. The unified messaging method 300 ends following the transmission316 of the message.

To further illustrate, FIG. 4 depicts a message transmission method 400for generating and transmitting a message in accordance with oneembodiment of the invention. As will be appreciated by those skilled inthe art, other messaging operations (e.g., receiving and displaying amessage) can be implemented in accordance with principles illustratedherein.

Initially, an abstract message is generated (402). Next, one or moreabstract features (or options) are displayed 404 for the user selection.When an abstract feature is selected (406), one or more states arestored (408) for the abstract message. Typically, the one or more stateshave been pre-defined for the selected feature. However, these statesmay also be dynamically defined at runtime.

In any case, after the one or more states have been stored (408) in theabstract message, it is determined (410) whether the abstract message iscompatible with a particular message type. Next, it is determined (412)whether the message type should be eliminated from furtherconsideration. Accordingly, if it is determined (410) the abstractmessage type is not compatible with the message type that particularmessage type is eliminated (412) from further consideration. Thereafter,it is determined (416) whether the message should be transmitted. If itis determined (416) that the message should be transmitted, one or morefeatures that can be selected are determined (418) and displayed 404 forthe user. It should be noted that these features are determined (418)based on the remaining viable message types. In other words, messagetypes that have been eliminated (412) are not considered when it isdetermined (418) what options should be displayed. When it is determined(416) that the message should be transmitted, it is determined (419)whether one or more message types can be used to transmit the message.If one or more message types may be used to transmit the message, apreferred message type is selected (420). The preferred message typecan, for example, be selected based on user preferences, or one or morerules which may have been predefined. In any case, the abstract messageis transformed (423) into a particular message type (protocol and/orformat). The message is transmitted (424) in accordance with aparticular message protocol and/or message format. The messagetransmission method 400 ends following the transmission 424 of themessage.

Appendix A provides additional examples that further illustrate bestmessaging.

The advantages of the invention are numerous. Different embodiments orimplementations may have one or more of the following advantages. Oneadvantage of the invention is that users can exchange messages onhandheld devices without having to understand numerous message types andprotocols. Another advantage of the invention is that less input isrequired from the user as undesirable options are eliminated. Yetanother advantage is that the invention can be implemented to enforcerules or preferences for exchanging messages. Still another advantage ofthe invention is users may be provided with abstract features and amessage type and a protocol can be automatically selected for the user.

The many features and advantages of the present invention are apparentfrom the written description, and thus, it is intended by the appendedclaims to cover all such features and advantages of the invention.Further, since numerous modifications and changes will readily occur tothose skilled in the art, it is not desired to limit the invention tothe exact construction and operation as illustrated and described.Hence, all suitable modifications and equivalents may be resorted to asfalling within the scope of the invention.

APPENDIX A

Assuming two message protocols of SMS & MMS, four (4) exemplary messagetypes: [T1] SMS-Text, [T2] SMS-Rich (EMS), [T3] MMS-Slideshow (SMIL),and [T4] MMS-Multipart (Inline) may be constructed and listed in orderof priority. Where Message type T1 represents a particular format (i.e.,text) using a particular protocol (e.g., the SMS protocol), and soforth.

Further assuming a set of features for these exemplary message types:[F1] Add-text, [F2] Add-Slide, [F3] Add-EMS-Image, [F4] Add-JPG-Image[F5] Send-to-Email, [F6] Send-to-Phone#, the features that each of theMessage types can support can, for example, be as follows:

-   F1 (T1, T2, T3, T4),-   F2 (T3),-   F3 (T2),-   F4 (T3, T4),-   F5 (T3, T4),-   F6 (T1, T2, T3)

It should be noted that a Feature (e.g., Add-text [F1]) can be used withone or more message types (e.g., T1, T2, T3, and T4).

It should also be noted that the feature set can be much larger and notsimply limited to types of content added, but could also includeformatting text or position messaging elements. In any case, each ofthese message types has a set of features that the user is able tochoose from while composing.

Following are some examples that demonstrate best messaging. However,actual determination rules may vary between implementations.

Case A - User starts free form composing Available Features to the userMessage would User actions (and feature owner) be sent as StartComposing F1 (T1, T2, T3, T4), T1 (the highest F2 (T3), priority) F3(T2), F4 (T3, T4), F5 (T3) F6 (T1, T2, T3) User adds a JPG F1 (T1, T2,T3, T4), T3 (the highest Image (F4) F2 (T3), priority) F4 (T3, T4) F5(T3) F6 (T1, T2, T3) User chooses Address Can only add email addressesT3 Send (F5) Sent T3

In case A, when a user selects “adds a JPG image” (F4) in compose mode,corresponding message types T3 and T4 are recognized. As s result,feature F3 will be eliminated as an option because feature F3 is notsupported for either message types T3 or T4. Next, the user chooses an“Address send” option. As a result, an email address feature (F5) isautomatically selected for the user because “add a JPG option” (F4) hasalready been selected. Finally, the JPG image is emailed as a type T3.

Case B - User chooses a phone number to send a message to from theirphone book Available Features to the Message would be User actions user(and feature owner) sent as Choose to send to a F1 (T1, T2, T3), T1 (thehighest phone number (F6) F2 (T3), priority) F3 (T2), F4 (T3, T4), F5(T3), F6 (T1, T2, T3) User adds a slide (F2) F1 (T3), T3 F2 (T3), F4(T3), F5 (T3), F6 (T3) Send T3

In case B, when the user chooses “send to a phone number” (F6) allmessage types will be available. However, when “add a slide” (F2) isselected, all message types expect message type T3 are eliminated as anoption.

We claim:
 1. A handheld communication device for transmission ofmessages to recipient devices, the handheld communication devicecomprising: a display; and a processor configured, in at least one modeof message composition, to: present a unified messaging interface to auser via the display for composition of messages which can betransmitted from the handheld communication device in at least twodifferent transmittal message types, including a Short Message Service(SMS) transmittal message type and a Multimedia Message Service (MMS)transmittal message type; and automatically select one or moretransmittal message types from the at least two different transmittalmessage types based at least in part on whether a feature, associatedwith a message via said unified messaging interface, is supported by theone or more transmittal message types, wherein, to perform the automaticselection of the one or more transmittal message types, the processor isconfigured to: automatically select an appropriate transmittal messagetype, from the at least two different transmittal message types, to beused for the transmission of the message, when the message has one ormore associated features which are supported by only one of the at leasttwo different transmittal message types; and automatically select apreferred transmittal message type, from the at least two differenttransmittal message types, to be used for the transmission of themessage, when the message has one or more associated features which aresupported by two or more of the at least two different transmittalmessage types.
 2. The handheld communication device of claim 1, whereinthe processor is configured, in the at least one mode of messagecomposition, to make one or more options available based on one or moreof the capabilities of the at least two different transmittal messagetypes, including at least one option which is not supported by one ormore of the at least two different transmittal message types.
 3. Thehandheld communication device of claim 2, wherein the at least oneoption which is not supported by one or more of the at least twodifferent transmittal message types includes an option to send to anemail address.
 4. The handheld communication device of claim 2, whereinthe at least one option which is not supported by one or more of the atleast two different transmittal message types includes an option to senda JPEG image.
 5. The handheld communication device of claim 1, whereinthe processor is configured, in the at least one mode of messagecomposition, to inhibit selection of a second option based on selectionby the user of a first option which is not supported by one or more ofthe at least two different transmittal message types during messagecomposition, thus leaving one or more viable transmittal message typesavailable, the second option not being supported by the one or moreviable transmittal message types.
 6. The handheld communication deviceof claim 5, wherein the processor is configured, in the at least onemode of message composition, to inhibit selection of an option to send aJPEG image based on only the SMS transmittal message type being leftavailable as the one or more viable transmittal message types.
 7. Thehandheld communication device of claim 1, wherein the processor isconfigured, in the at least one mode of message composition, to inhibituse of at least one transmittal message type for the transmission of themessage based on selection by the user of an option which is notsupported by the at least one transmittal message type.
 8. The handheldcommunication device of claim 7, wherein the processor is configured, inthe at least one mode of message composition, to automatically selectthe preferred transmittal message type or the appropriate transmittalmessage type during further message composition based on selection bythe user of an option which is not supported by at least one of the atleast two different transmittal message types.
 9. The handheldcommunication device of claim 2, wherein the at least one option whichis not supported by one or more of the at least two differenttransmittal message types includes an option to send to an emailaddress, and wherein the processor is configured, in the at least onemode of message composition, to inhibit use of the SMS transmittalmessage type based on selection by the user of the option to send to anemail address.
 10. The handheld communication device of claim 1, whereinthe at least two different transmittal message types include a furthertransmittal message type in addition to the SMS transmittal message typeand the MMS transmittal message type.
 11. The handheld communicationdevice of claim 1, wherein the processor is configured to automaticallydetermine the preferred transmittal message type based on one or moreuser preference settings.
 12. The handheld communication device of claim1, wherein the processor is configured, in the at least one mode ofmessage composition, to automatically select the MMS transmittal messagetype when the message includes image content.
 13. The handheldcommunication device of claim 1, wherein the processor is configured, inthe at least one mode of message composition, to automatically selectthe SMS transmittal message type to be the preferred transmittal messagetype when the message includes only text content.
 14. The handheldcommunication device of claim 1, wherein the processor is configured, inthe at least one mode of message composition, to send the message usingthe SMS transmittal message type via a Short Message Service Centermessaging server if the SMS transmittal message type is selected to beused for the transmission of the message, and send the message using theMMS transmittal message type via a Multimedia Messaging Service Centermessaging server if the MMS transmittal message type is selected to beused for the transmission of the message.
 15. The handheld communicationdevice of claim 1, wherein each of the at least two differenttransmittal message types corresponds to a different communicationsnetwork path.
 16. The handheld communication device of claim 15, whereinwhen the transmittal message type is an SMS transmittal message type,the message is sent via a communications network path including a ShortMessage Service Center and when the transmittal message type is an MMStransmittal message type, the message is sent via a communicationsnetwork path including a Multimedia Messaging Service Center.
 17. Thehandheld communication device of claim 1, wherein the unified messaginginterface includes a unified messaging inbox in which both received SMSmessages and received MMS messages are included.
 18. The handheldcommunication device of claim 1, wherein the unified messaging interfaceis also for the viewing of one or more sent messages using the at leasttwo different transmittal message types, and wherein the unifiedmessaging interface does not indicate which of the at least twodifferent transmittal message types was used for the one or more sentmessages.
 19. A method of operating a handheld communication device fortransmission of messages to recipient devices, the handheldcommunication device comprising a display and at least one mode ofmessage composition, the method comprising: presenting a unifiedmessaging interface to a user via the display for composition ofmessages which can be transmitted from the handheld communication devicein at least two different transmittal message types, including a ShortMessage Service (SMS) transmittal message type and a Multimedia MessageService (MMS) transmittal message type; and automatically selecting oneor more transmittal message types from the at least two differenttransmittal message types based at least in part on whether a feature,associated with a message via said unified messaging interface, issupported by the one or more transmittal message types, wherein theautomatically selecting the one or more transmittal message typescomprises: automatically selecting an appropriate transmittal messagetype, from the at least two different transmittal message types, to beused for the transmission of the message, when the message has one ormore associated features which are supported by only one of the at leasttwo different transmittal message types; and automatically selecting apreferred transmittal message type, from the at least two differenttransmittal message types, to be used for the transmission of themessage, when the message has one or more associated features which aresupported by two or more of the at least two different transmittalmessage types.
 20. The method of claim 19, wherein, in the at least onemode of message composition, the unified messaging interface makes oneor more options available based on one or more of the capabilities ofthe at least two different transmittal message types, including at leastone option which is not supported by one or more of the at least twodifferent transmittal message types.
 21. The method of claim 20, whereinthe at least one option which is not supported by one or more of the atleast two transmittal different message types includes an option to sendto an email address.
 22. The method of claim 20, wherein the at leastone option which is not supported by one or more of the at least twodifferent transmittal message types includes an option to send a JPEGimage.
 23. The method of claim 19, wherein, in the at least one mode ofmessage composition, the method comprises inhibiting selection of asecond option based on selection by the user of a first option which isnot supported by one or more of the at least two different transmittalmessage types during message composition, thus leaving one or moreviable transmittal message types available, the second option not beingsupported by the one or more viable transmittal message types.
 24. Themethod of claim 23, wherein, in the at least one mode of messagecomposition, the method comprising inhibiting selection of an option tosend a JPEG image based on only the SMS transmittal message type beingleft available as the one or more viable transmittal message types. 25.The method of claim 19, wherein, in the at least one mode of messagecomposition, the method comprises inhibiting use of at least onetransmittal message type of the at least two different transmittalmessage types based on selection by the user of an option which is notsupported by the at least one transmittal message type.
 26. The methodof claim 25, wherein, in the at least one mode of message composition,the method comprises automatically selecting the preferred transmittalmessage type or automatically selecting the appropriate transmittalmessage type during further message composition based on selection bythe user of an option which is not supported by at least one of the atleast two different transmittal message types.
 27. The method of claim20, wherein the option which is not supported by one or more of the atleast two different transmittal message types includes an option to sendto an email address, and wherein, in the at least one mode of messagecomposition, the method comprises inhibiting use of the SMS transmittalmessage type for the transmission of the message based on selection bythe user of the option to send to an email address.
 28. The method ofclaim 19, wherein the at least two different transmittal message typesinclude a further transmittal message type in addition to the SMStransmittal message type and said MMS transmittal message type.
 29. Themethod of claim 19, wherein, in the at least one mode of messagecomposition, the automatically selecting a preferred transmittal messagetype is based on one or more user preference settings.
 30. The method ofclaim 19, wherein, in the at least one mode of message composition, theMMS transmittal message type is automatically selected when the messageincludes image content.
 31. The method of claim 19, wherein, in the atleast one mode of message composition, the SMS transmittal message typeis automatically selected to be the preferred transmittal message typewhen the message includes only text content.
 32. The method of claim 19,wherein, in the at least one mode of message composition, the methodcomprises: sending the message using the SMS transmittal message typevia a Short Message Service Center messaging server if the SMStransmittal message type is selected to be used for the transmission ofthe message; and sending the message using the MMS transmittal messagetype via a Multimedia Messaging Service Center messaging server if theMMS transmittal message type is selected to be used for the transmissionof the message.
 33. The method of claim 19, wherein each of the at leasttwo different transmittal message types corresponds to a differentcommunications network path.
 34. The method of claim 33, wherein, in theat least one mode of message composition, the method comprises: sendingthe message via a communications network path including a Short MessageService Center when the transmittal message type is an SMS transmittalmessage type; and sending the message via a communications network pathincluding a Multimedia Messaging Service Center when the transmittalmessage type is an MMS transmittal message type.
 35. The method of claim19, wherein the unified messaging interface includes a unified messaginginbox in which both received SMS messages and received MMS messages areincluded.
 36. The method of claim 19, comprising viewing one or moresent messages using the at least two different transmittal message typesin the unified messaging interface, and wherein the unified messaginginterface does not indicate which of the at least two differenttransmittal message types was used for the one or more sent messages.37. A non-transitory computer-readable storage medium storingcomputer-readable instructions thereon, the computer-readableinstructions executable by a processor of a handheld communicationdevice to perform a method for transmission of messages from thehandheld communication device to recipient devices, the handheldcommunication device including a display and at least one mode ofmessage composition, the method comprising: presenting a unifiedmessaging interface to a user via the display for the composition ofmessages which can be transmitted from the handheld communication devicein at least two different transmittal message types, including a ShortMessage Service (SMS) transmittal message type and a Multimedia MessageService (MMS) transmittal message type; and automatically selecting oneor more transmittal message types from the at least two differenttransmittal message types based at least in part on whether a feature,associated with a message via said unified messaging interface, issupported by the one or more transmittal message types, wherein theautomatically selecting the one or more transmittal message typescomprises: automatically selecting an appropriate transmittal messagetype, from the at least two different transmittal message types, to beused for the transmission of the message, when the message has one ormore associated features which are supported by only one of the at leasttwo different transmittal message types; and automatically selecting apreferred transmittal message type, from the at least two differenttransmittal message types, to be used for the transmission of themessage, when the message has one or more associated features which aresupported by two or more of the at least two different transmittalmessage types.
 38. The non-transitory computer-readable storage mediumof claim 37, wherein, in the at least one mode of message composition,the unified messaging interface makes one or more options availablebased on one or more of the capabilities of the at least two differenttransmittal message types, including at least one option which is notsupported by one or more of the at least two different transmittalmessage types.
 39. The non-transitory computer-readable storage mediumof claim 38, wherein the at least one option which is not supported byone or more of the at least two different transmittal message typesincludes an option to send to an email address.
 40. The non-transitorycomputer-readable storage medium of claim 38, wherein the at least oneoption which is not supported by one or more of the at least twodifferent transmittal message types includes an option to send a JPEGimage.
 41. The non-transitory computer-readable storage medium of claim37, wherein, in the at least one mode of message composition, the methodcomprises inhibiting selection of a second option based on selection bythe user of a first option which is not supported by one or more of theat least two different transmittal message types during messagecomposition, thus leaving one or more viable transmittal message typesavailable, the second option not being supported by the one or moreviable transmittal message types.
 42. The non-transitorycomputer-readable storage medium of claim 41, wherein, in the at leastone mode of message composition, the method comprises inhibitingselection of an option to send a JPEG image based on only the SMStransmittal message type being left available as the one or more viabletransmittal message types.
 43. The non-transitory computer-readablestorage medium of claim 37, wherein, in the at least one mode of messagecomposition, the method comprises inhibiting use of at least onetransmittal message type of the at least two different transmittalmessage types based on selection by the user of an option which is notsupported by the at least one transmittal message type.
 44. Thenon-transitory computer-readable storage medium of claim 43, wherein, inthe at least one mode of message composition, the method comprisesautomatically selecting the preferred transmittal message type orautomatically selecting the appropriate transmittal message type duringfurther message composition based on selection by the user of an optionwhich is not supported by at least one of the at least two differenttransmittal message types.
 45. The non-transitory computer-readablestorage medium of claim 38, wherein the option which is not supported byone or more of the at least two different transmittal message typesincludes an option to send to an email address, and wherein, in the atleast one mode of message composition, the method comprises inhibitinguse of the SMS transmittal message type for the transmission of themessage based on selection by the user of the option to send to an emailaddress.
 46. The non-transitory computer-readable storage medium ofclaim 37, wherein the at least two different transmittal message typesinclude a further transmittal message type in addition to the SMStransmittal message type and said MMS transmittal message type.
 47. Thenon-transitory computer-readable storage medium of claim 37, wherein, inthe at least one mode of message composition, the automaticallyselecting a preferred transmittal message type is based on one or moreuser preference settings.
 48. The non-transitory computer-readablestorage medium of claim 37, wherein, in the at least one mode of messagecomposition, the MMS transmittal message type is automatically selectedwhen the message includes image content.
 49. The non-transitorycomputer-readable storage medium of claim 37, wherein, in the at leastone mode of message composition, the SMS transmittal message type isautomatically selected to be the preferred transmittal message type whenthe message includes only text content.
 50. The non-transitorycomputer-readable storage medium of claim 37, wherein, in the at leastone mode of message composition, the method comprises: sending themessage using the SMS transmittal message type via a Short MessageService Center messaging server if the SMS transmittal message type isselected to be used for the transmission of the message; and sending themessage using the MMS transmittal message type via a MultimediaMessaging Service Center messaging server if the MMS transmittal messagetype is selected to be used for the transmission of the message.
 51. Thenon-transitory computer-readable storage medium of claim 37, whereineach of the at least two different transmittal message types correspondsto a different communications network path.
 52. The non-transitorycomputer-readable storage medium of claim 51, wherein, in the at leastone mode of message composition, the method comprises: sending themessage via a communications network path including a Short MessageService Center when the transmittal message type is an SMS transmittalmessage type; and sending the message via a communications network pathincluding a Multimedia Messaging Service Center when the transmittalmessage type is an MMS transmittal message type.
 53. The non-transitorycomputer-readable storage medium of claim 37, wherein the unifiedmessaging interface includes a unified messaging inbox in which bothreceived SMS messages and received MMS messages are included.
 54. Thenon-transitory computer-readable storage medium of claim 37, comprisingviewing one or more sent messages using the at least two differenttransmittal message types in the unified messaging interface, andwherein the unified messaging interface does not indicate which of theat least two different transmittal message types was used for the one ormore sent messages.